home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Almathera Ten Pack 2: CDPD 1
/
Almathera Ten on Ten - Disc 2: CDPD 1.iso
/
pd
/
351-375
/
366
/
doserror
/
doserror.doc
< prev
next >
Wrap
Text File
|
1995-03-14
|
4KB
|
95 lines
DOSError V2.0
~~~~~~~~~~~~~
This program is not public domain, nor shareware, but what I choose to
call "USEWARE", meaning that I want people to use it ! Shareware is a
little painful because you are morally obligated to pay if you use it,
meaning you would rather use a PD one....so I want you to use it, and
if you want me to write more, then send money, but DON'T in ANY WAY
feel obligated. It is not PD, because I hold the copyright over it.
I've included the source in the release, so that people may learn
assembly...the best programming language....or so that they may edit
it to suit themselves, but my name MUST remain somewhere in the program,
and it may not be used for any commercial or money-gaining venture without
my written permission. I also take no responsibility for damage done
with my program or source. If you would like to send $20 to me, I'll
send you the latest version of DOSError, and a list of my current programs
written, and you will notified by mail of new programs by me, or updates
of older programs...so I hope that's worth your while !
DOSError is a neato program I wrote a little while back to help me when
the stupid DOS yelled something like "DOS ERROR #221" or something
equally as stupid.....I would then simply type DOSERROR 221 and my neat
program would output a small message.
Ok, so that was V1.0, and very little has changed. I was a little annoyed
one time when the error description didn't help one little bit, meaning
I had to go to the DOS manual, defeating the program's purpose. So, the
descriptions have been verbosified (?) a bit. Also, to serve the public,
a request from Gavin Williamson has been fulfilled, DOSError now runs
from the workbench.
So, using from workbench, you double click the neat icon and up pops a
CON: window, asking for the argument. You can type ALL to get a full
list of errors, ? to get a usage message, or the number to get the error
description.
The ALL descriptions fly off the screen, and its no intention of mine to
fix this. The only reason I put the ALL command in is to allow you to
make a DOS Error list of your own by :
DOSError >Ram:ErrorList ALL
and then you have a file called ErrorList containing all the errors, or
you could do
DOSError >prt: ALL
and get a printout of the errors.
From the CLI, you can just type DOSError and enter the argument the same
way as from the Workbench, or you can enter the argument on the same line
(this is the way I use it, since I'm a CLI freak....)
e.g.
DOSError 121
Will output:
DOS Error 121 : FILE NOT OBJECT
The called file cannot be executed.
and so now its all up to you to copy my program to your c: directory and
use it when you need it. I've used it many times, but in my recent
decision to go public with some of my programming, well, here it is !
If you have any problems, demos, suggestions, money, porsches,
or anything else to send to me, then please do so !!!
Robert Lang
(EDGEWARE)
P.O. Box 127
CARDIFF NSW 2285
AUSTRALIA
All sensible letters will be answered. Alternatively, you can netmail me
on Cybertron BBS, I'm the Assistant SYSOP there, so around a lot....
CYBERTRON BBS Ph: 049-602383 (AUSTRALIA)
FidoNet 3:711/496 Signet: 28:2100/104
Or as a last resort, ring me on 049-508189....but doing a Computer
Engineering degree at Newcastle Uni keeps me on the move, so I'm hard to
catch, and please don't expect return calls that are long distance,
because I just can't afford it....sorry !
Well, to finish, all my programs are dedicated to Suzanne Day,
my girlfriend, who puts up with a lot of me and computers somehow....
authors dedicate books, so I'm going to dedicate programs.
Please USE it, and let me know what you think !!!!!!!
Robert Lang.